
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
<title>CSS Syntax Module Level 3 Disposition of Comments for 2013-11-05 LCWD</title>
<style type="text/css">
  .a  { background: lightgreen }
  .d  { background: lightblue  }
  .r  { background: orange     }
  .fo { background: red        }
  .open   { border: solid red; padding: 0.2em; }
  :target { box-shadow: 0.25em 0.25em 0.25em;  }
</style>

<h1>CSS Syntax Module Level 3 Disposition of Comments for 2013-11-05 LCWD</h1>

<p>Last call document: <a href="http://www.w3.org/TR/2013/WD-css-syntax-3-20131105/">http://www.w3.org/TR/2013/WD-css-syntax-3-20131105/</a>

<p>Editor's draft: <a href="http://dev.w3.org/csswg/css-syntax-3/">http://dev.w3.org/csswg/css-syntax-3/</a>

<p>The following color coding convention is used for comments:</p>

<ul>
 <li class="a">Accepted or Rejected and positive response
 <li class="r">Rejected and no response
 <li class="fo">Rejected and negative response
 <li class="d">Deferred
 <li class="oi">Out-of-Scope or Invalid and not verified
</ul>

<p class=open>Open issues are marked like this</p>

<p>An issue can be closed as <code>Accepted</code>, <code>OutOfScope</code>,
<code>Invalid</code>, <code>Rejected</code>, or <code>Retracted</code>.
<code>Verified</code> indicates commentor's acceptance of the response.</p>
		<pre class='a' id='issue-1'>
Issue 1. <a href='#issue-1'>#</a>
Summary:  Parsing a declaration should allow white space only values
From:     Cameron McCormack
Comment:  <a href='http://lists.w3.org/Archives/Public/www-style/2013Dec/0156.html'>http://lists.w3.org/Archives/Public/www-style/2013Dec/0156.html</a>
Response: <a href='http://lists.w3.org/Archives/Public/www-style/2013Dec/0162.html'>http://lists.w3.org/Archives/Public/www-style/2013Dec/0162.html</a>
Closed:   Invalid
Verified: <a href='http://lists.w3.org/Archives/Public/www-style/2013Dec/0163.html'>http://lists.w3.org/Archives/Public/www-style/2013Dec/0163.html</a></pre>
<pre class='a' id='issue-2'>
Issue 2. <a href='#issue-2'>#</a>
Summary:  Parsing a declaration should allow white space only values
From:     I18N WG
Comment:  <a href='http://www.w3.org/International/track/products/54'>http://www.w3.org/International/track/products/54</a>
Response: <a href='http://lists.w3.org/Archives/Public/www-style/2014Jan/0060.html'>http://lists.w3.org/Archives/Public/www-style/2014Jan/0060.html</a>
Closed:   Accepted
Verified: <a href='http://lists.w3.org/Archives/Public/www-style/2014Jan/0362.html'>http://lists.w3.org/Archives/Public/www-style/2014Jan/0362.html</a></pre>
<pre class='a' id='issue-3'>
Issue 3. <a href='#issue-3'>#</a>
Summary:  Align @charset encoding detection with at-rule parsing rules
From:     I18N WG
Comment:  <a href='http://www.w3.org/International/track/products/54'>http://www.w3.org/International/track/products/54</a>
Response: <a href='http://lists.w3.org/Archives/Public/www-style/2014Jan/0362.html'>http://lists.w3.org/Archives/Public/www-style/2014Jan/0362.html</a>
Closed:   Rejected
Verified: <a href='http://lists.w3.org/Archives/Public/www-style/2014Feb/0214.html'>http://lists.w3.org/Archives/Public/www-style/2014Feb/0214.html</a></pre>
<pre class='a' id='issue-4'>
Issue 4. <a href='#issue-4'>#</a>
Summary:  Content-based encoding detection should only require a small bounded amount of input
From:     Henri Sivonen
Comment:  <a href='http://lists.w3.org/Archives/Public/www-style/2014Jan/0527.html'>http://lists.w3.org/Archives/Public/www-style/2014Jan/0527.html</a>
Response: <a href='http://lists.w3.org/Archives/Public/www-style/2014Jan/0537.html'>http://lists.w3.org/Archives/Public/www-style/2014Jan/0537.html</a>
Closed:   Accepted
Verified:</pre>
